User Manager System and Message Overviews Document Version: 5.2 Date: March 19, 2014
Copyright © 2009-2023 Jeppesen. All rights reserved.
Your use of the AIM Bookshelf and all supporting documentation is subject to a separate license agreement between you and Jeppesen, a copy of which is included in the zip file or can be obtained from Jeppesen.
The AIM Bookshelf is delivered "AS IS" without warranty of any kind and is not guaranteed to be free from errors or defects. You rely on the AIM Bookshelf at your own risk. No support for the AIM Bookshelf is implied through its publication. The AIM Bookshelf is intended solely for use as a reference and examples of interfaces to Jeppesen systems. Jeppesen may revise, update or cease publication at any time, without notice. Building to the specifications set forth in the AIM Bookshelf does not mean that your intended integration needs will be met or that an interface will function as documented. We recommend contacting Jeppesen directly to discuss professional services options with respect to production application integration and validation efforts.
Document Revision History The following revision history table reflects all substantive changes to this document.
Table Of Contents
1 IntroductionThis document defines the interfaces which govern the interchange of data between a User Manager system and other systems within an Airline Operation Center (AOC). Each AOC interface is represented by a message described in an associated XSD (XML Schema Definition). The XSD defines and enforces the required, optional, and conditional data that can be included in a message. User Manager system is an AOC shared service for managing users as well as application roles and permissions. 1.1 AudienceThe intended audience for this document includes existing and potential Jeppesen customers, integration partners, and personnel with roles associated with application architecture, application development, system testing, implementation, and application support within User Manager. 1.2 ScopeThis document discusses the User Manager messages currently supported by the Jeppesen Solution Integrator. Each message description includes the following:
Other data interfaces or formats not included in this document will be considered custom and not supported. 1.3 XML Schema/XSDThe XML schema for this ICD is published in the following file: UserManagement.xsd 2 Message SummaryTable 2-1 lists the messages that can be sent or handled by the application. The messages originated by this application (messages that begin with “UM”) are further discussed in Section 3 AOC Interface Messages.
3 AOC Interface MessagesThe following messages are processed by the User Manager system. NOTE: When a user is created using the User Manager, the user's password is stored in the database using MD5 encryption. The value of the password element of LoginType elements in UM messages (UM001, UM002) must already be MD5 encrypted by the client product. Authentication is based on an exact match between the two strings. To ensure client products can reproduce the encrypted password string created by the User Manager application, client products should follow these guidelines:
Example: the password abcd1234 should be represented by the encrypted string: 4Z1c1a8DeNoF9j+JHHRnrw== 3.1 UM001 – User Login3.1.1 Message OverviewAOC User Manager provides a single interface through which AOC administrators can create users and manage their access to all integrated applications within an Airline Operation Center. With this behind-the-scenes application, user accounts are created and configured to allow role-based access to any product in their AOC. The end-users of various products within an AOC log onto a product through the product’s standard logon screen, the product sends a message to AOC User Manager to authenticate the user, and then AOC User Manager returns the end-user’s specific permissions and settings for that product. This message features both a Request (from a product to User Manager) and a Response (from User Manager back to the product). UM001 Request: UM001 Response: 3.1.2 Message System FlowThis message interacts with the systems as shown in Figure 1. 3.1.3 Message DetailsThe following table provides details on the message version and includes links to the message’s technical specification.
3.2 UM002 – Change Password3.2.1 Message OverviewAOC Administrators can manage users’ passwords for all integrated AOC applications from the AOC User Manager. General password settings such as expiration rules and password complexity are set using the User Manager application at the corporation level. Individual passwords are set and managed in User Manager at the user level. This message features both a Request (from a product to User Manager) and a Response (from User Manager back to the product). UM002 Request
UM002 Response Possible errors include not meeting the password complexity requirements as defined in User Manager or attempting to use a previously-used password. 3.2.2 Message System FlowThis message interacts with the systems as shown in Figure 2. 3.2.3 Message DetailsThe following table provides details on the message and includes links to the message’s technical specification.
|